목차
Lean software development
LSD 의 원칙 중 하나인 Decide as late as possible 의 도구.
“
The moment at which failing to make a decision eliminates an important alternative. If commitments are delayed beyond the last responsible moment, then decisions are made by default, which is generally not a good approach to making decisions. —p57, Chapter 3, Lean software development (book)
Some tactics:
“
Share partially complete design information
Organize for direct, worker-to-worker collaboration
Develop a sense of how to absorb changes
Develop a sense of what is critically important in the domain
Develop a sense of when decisions must be made
Develop a quick response capability
—p57-60, Chapter 3, Lean software development (book)
목차 관련 글 Set-based development 이 글을 인용: “In addition, talking about constraints instead of choices defers making choices until they have to be made, tha…” 이터레이션 관련 절: [[Lean software development]] Amplify learning 관련 절: [[Lean software development|린 소프트웨어 개발]]의 원칙 중 하나 Self determination “Those who made proposals are expected to be responsible for implementing them - immediately.” Wastes of software development “One of the biggest wastes in software development is usually waiting for things to happen.” 옵션 기반 사고 관련 절: [[Lean software development]] 큐잉 이론 “Thus, with iterative development, it is critically important that you do not have a bottleneck at testing. --p79” Pull system 관련 절: [[Lean software development]] Build integrity in “How can you be sure that a good architecture will emerge?” Empower the team 관련 절: [[Lean software development]]의 원칙 중 하나 소프트웨어 테스팅의 교훈들 “Rather than developing a large suite of tests in advance of testing, develop tests as you need them.” Leadership “Distinction between managers and leader (Chapter 5, Lean software development (book)):” 전문성 “Software development is a complex endeavor with many areas of specialized knowledge.” 최대한 빠른 인도 관련 절: [[Lean software development]]의 원칙 중 하나 전체를 보기 관련 절: [[Lean software development]]의 원칙 중 하나 Value stream mapping “Mapping your value stream is a good way to start discovering the waste in your software development process.” Conceptual integrity “How can you be sure that a good architecture will emerge?” 리팩토링 관련 절: [[Lean software development]] 내가 읽은 책들 주제어가 겹침 낭비 제거 관련 절: [[Lean software development|린 소프트웨어 개발]]의 원칙 중 하나